Medical image based collaboration

ABSTRACT

Medical image based collaboration system and methods are provided. A collaboration server 40 creates a medical image based case in response to a request from a requesting system 10 and populates the case with the minimum required information comprising at least a digital medical image and a case number. The collaboration server 40 provides the medical image based case to a consulting system 30 and receives analysis information in response. The collaboration server 40 stores the analysis information in association with the medical image based case and provides the analysis information to the consulting system 30 to complete the medical image based collaboration.

RELATED APPLICATION

The present application is a continuation of U.S. patent applicationSer. No. 14/432,178, filed on Mar. 27, 2015, which is a national stageentry of International Patent Application No. PCT/US2013/032583, filedon Mar. 15, 2013, which claims priority to U.S. Provisional PatentApplication No. 61/706,466, filed on Sep. 27, 2012, which are all herebyincorporated herein by reference as if set forth in full.

BACKGROUND Field of the Invention

The present invention generally relates to collaboration surroundingmedical images and more specifically relates to primary diagnoses,secondary opinions, and collaboration between professionals facilitatedby medical images.

Related Art

In conventional medical image based cases, an individual medicalprofessional may feel uncomfortable rendering a final diagnosis on adifficult case and/or a case outside his or her area of expertise. Sucha medical professional may want to consult with a peer or a recognizedexpert in the particular subject matter of the medical image based case.Similarly, a medical practice group or hospital or health care companymay desire to consolidate its diagnoses for medical image based cases.Such consolidation may be within the medical group or hospital or healthcare company or may be external to the medical group or hospital orhealth care company. Conventional systems based upon glass microscopeslides or proprietary medical imaging systems fail to allow easy,scalable and reliable collaboration on medical image based cases.Digital imaging for medical image based cases holds the promise ofallowing some level of collaboration but has not been able to overcomethe significant technical and administrative challenges associated withmedical image based collaboration. Therefore, what is needed is a systemand method that provides for easy, scalable and reliable medical basedimage collaboration to meet the needs of individual medicalprofessionals while also meeting the needs of medical groups andhospitals and health care companies and the like.

SUMMARY

Accordingly, a medical image based collaboration system is describedherein that provides easy, scalable and reliable solutions to theproblems described above. The system includes a collaboration serverthat creates a medical image based case and establishes a set of minimumrequired information to complete the case. The collaboration servercreates the medical image based case in response to a request from arequesting system and the collaboration server cooperates with therequesting system to populate the medical image based case with at leasta digital medical image and a case number to complete the case. Thecollaboration server provides the medical image based case to aconsulting system and receives analysis information in response. Thecollaboration server stores the analysis information in association withthe medical image based case and provides the analysis information tothe consulting system to complete the medical image based collaboration.

Other features and advantages of the present invention will become morereadily apparent to those of ordinary skill in the art after reviewingthe following detailed description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The structure and operation of the present invention will be understoodfrom a review of the following detailed description and the accompanyingdrawings in which like reference numerals refer to like parts and inwhich:

FIG. 1 is a network diagram illustrating an example system for medicalimage based collaboration according to an embodiment of the invention;

FIG. 2 is a block diagram illustrating an example smart medical imagecapture device in a system for medical image based collaborationaccording to an embodiment of the invention;

FIG. 3 is a block diagram illustrating an example server in a system formedical image based collaboration according to an embodiment of theinvention;

FIG. 4 is a flow diagram illustrating an example process for initiatingmedical image based collaboration by a requesting system according to anembodiment of the invention;

FIG. 5 is a flow diagram illustrating an example process forautomatically initiating medical image based collaboration by a smartmedical image capture device according to an embodiment of theinvention;

FIG. 6 is a flow diagram illustrating an example process for creating acomplete medical image based case according to an embodiment of theinvention;

FIG. 7 is a flow diagram illustrating an example process for configuringa smart medical image capture device in accordance with medical imagebased case parameters according to an embodiment of the invention;

FIG. 8 is a flow diagram illustrating an example process for searching adirectory of consulting systems according to an embodiment of theinvention;

FIG. 9 is a block diagram illustrating an example workflow in a systemfor medical image based collaboration according to an embodiment of theinvention; and

FIG. 10 is a block diagram illustrating an example wired or wirelessprocessor enabled device that may be used in connection with variousembodiments described herein.

DETAILED DESCRIPTION

Certain embodiments disclosed herein provide for medical imaging basedcollaboration. For example, one method disclosed herein allows for arequesting system to cooperate with a collaboration server system tocreate a medical image based case on the server, establish a minimumdata set required to complete the case, provide the completed case to aconsulting system, update the case with analysis information from theconsulting system and receive the updated case from the server system.After reading this description it will become apparent to one skilled inthe art how to implement the invention in various alternativeembodiments and alternative applications. However, although variousembodiments of the present invention will be described herein, it isunderstood that these embodiments are presented by way of example only,and not limitation. As such, this detailed description of variousalternative embodiments should not be construed to limit the scope orbreadth of the present invention as set forth in the appended claims.

FIG. 1 is a network diagram illustrating an example system 100 formedical image based collaboration according to an embodiment of theinvention. In the illustrated embodiment, the system 100 comprises anetwork 90 that communicatively couples a plurality of entities. Itshould be noted that an entity may be an organization such as a companyor a medical practice group or it may be one or more computer serverdevice or one or more medical image capture devices or the like.Throughout this description, entities may be alternatively referred toas systems or institutions or the like.

In the illustrated embodiment, the network 90 communicatively couplesone or more requesting systems 10 and 20, one or more consulting systems30, one or more collaboration servers 40, one or more smart medicalimage capture systems 50, one or more medical image capture systems 60and one or more repository systems 70. As shown in FIG. 1 , each ofthese systems has one or more data storage areas 15, 24, 27, 28, 35, 45,55, 65 and 75, which may include both persistent and volatile storage.The network 90 can be a public or private network, a wired or wirelessnetwork or any combination including public and private and wired andwireless. Network 90 can include a personal area network (“PAN”), alocal area network (“LAN”), a wide area network (“WAN”), or adistributed combination of networks collectively comprising a globalcommunications network such as the Internet. Network 90 can be an ad hocnetwork or a persistent network and can be fixed in location, be mobile,or network 90 may comprise a combination of fixed and mobile components.Additionally, network 90 may carry communications corresponding to asingle network protocol or corresponding to multiple network protocols.

Requesting system 10 is configured to interface with the server 40 toinitiate the creation of one or more medical image based cases andfacilitate the completion of such cases. Requesting system 10 mayinclude one or more computer devices capable of autonomous operation toaccomplish the above described creation and completion of medical imagebased cases. In one embodiment, the requesting system 10 is a hospitalor medical practice group with one or more professionals tasked withrendering diagnoses based in part on medical images. The requestingsystem 10 may or may not include one or more smart medical image capturedevices (“SMICD”) and other medical image capture devices.

For example, in one embodiment, a medical practice group 20 comprises arequesting system 22 and one or more smart medical image capture devices26 and one or more other medical image capture devices 25. In such anembodiment, the group 20 may also include a laboratory informationsystem (“LIS”)—not separately illustrated in FIG. 1 —and othersystems—also not shown in FIG. 1 —that store information related to amedical image based case.

In an alternative embodiment, requesting system 10 operates over network90 in cooperation with one or more smart medical image capture devices50 and/or one or more other medical image capture devices 60. In oneembodiment, the difference between a smart medical image capture device50 and a medical image capture device 60 is that the smart medical imagecapture device 50 is configured to interface with the one or morecollaboration servers 40 to initiate the creation of one or more medicalimage based cases and facilitate the completion of such cases. Both thesmart medical image capture device 50 and the medical image capturedevice 60 are capable of storing the digital medical images theycapture. Otherwise, the one or more smart medical image capture devices50 and the one or more medical image capture devices 60 are devices thatare capable of capturing and storing medical images. Some examples ofsuch devices include digital pathology systems, magnetic resonanceimaging (“MRI”) systems, computed axial tomography (“CAT”) systems, andX-ray systems just to name a few. Other medical imaging systems may alsobe employed in the system 100 as will be understood by those skilled inthe art.

In one embodiment, the repository 70 is configured to store medicalimage based cases and provide decision support to professionals asrequested for medical image based diagnoses. The repository 70 can alsoadvantageously store important collections of medical images fortraining and educational purposes.

Collaboration server 40 is configured to interface with requestingsystems 10 and 20, consulting systems 30, smart medical image capturedevices 50, medical image capture devices 60, and repositories 70 toimplement and facilitate medical image based collaboration. Thecollaboration server 40 creates and manages medical image based casesand manages the workflow between a requesting system 10 (and any relatedsystems such as the aforementioned LIS) and a consulting system 30 andany smart medical image capture devices 50 and the repository 70. Itshould be noted that a medical image based case is an electronicallystored data set that comprises at least a medical image and anidentifier referred to herein as a case number.

In operation, the system 100 is configured such that the requestingsystem 10 initially requests that a medical image based case be createdby the collaboration server 40. This can be accomplished by an operatorat the requesting system 10 logging into the collaboration server 40 andsubmitting the request. This can also be accomplished by a smart medicalimage capture device 50 sending an electronic request communication tothe collaboration server 40 over the network 90. The collaborationserver 40 cooperates with the requesting system 10 (operator or SMICD)to create the case and define the minimum data set required for the caseto be complete. The collaboration server 40 and/or the requesting system10 then cooperate to provide the collaboration server 40 with thenecessary information for the case to be complete and the collaborationserver 40 stores the case in a local or remote data storage areaaccessible by the collaboration server 40.

Once the case is completed, the collaboration server 40 provides noticeto the consulting system 30 (e.g., by sending an electronic noticecommunication to the consulting system 30 over the network 90) and theconsulting system 30 is allowed to access the medical image based caseon the server 40. In one embodiment, the collaboration server 40provides the medical image based case information to the consultingsystem 30 via the network 90 in response to one or more requests for theinformation and none of the medical image based case information ispersistently stored in a data storage area the consulting system 30.

The consulting system 30 is configured to provide the collaborationserver 40 with analysis information based on the provided medical imagebased case information and the collaboration server 40 is configured toreceive that information and store that information in association withor as part of the medical image based case. The collaboration server 40can then send a notice to the requesting system 10 and provide theanalysis information to the requesting system 10, for example via thenetwork 90 in response to one or more requests for the analysisinformation from the requesting system 10.

For example, in one embodiment, the collaboration server 40 creates amedical image based case and receives first medical image based caseinformation comprising a digital medical image from the requestingsystem 10. The collaboration server 40 assigns a case number and withthe case number and the digital medical image, the medical image basedcase is considered complete. The collaboration server 40 notifies theconsulting system 30 and provides the medical image based caseinformation to the consulting system 30 and receives analysisinformation in response. The collaboration server 40 stores the analysisinformation as part of or in association with the medical image basedcase and notifies the requesting system 10 that the analysis informationis available for review. The collaboration server 40 provides theanalysis information to the requesting system 30 to complete the medicalimage based collaboration. The collaboration server 40 may also transmitthe medical image based case to the repository 70 if the medical imagebased case meets certain predetermined criteria for inclusion in therepository 70.

FIG. 2 is a block diagram illustrating an example smart medical imagecapture device 50 in a system for medical image based collaborationaccording to an embodiment of the invention. In the illustratedembodiment, the SMICD 50 comprises a configuration module 200, an imagecapture module 210 and an upload module 220. The SMICD 50 also has adata storage area 55, which may include both persistent and volatilestorage as described above.

The configuration module 200 is configured to establish the parametersunder which the SMICD 50 will capture medical image data. For example,in a microscope based imaging system, the configuration module 200 mayset a parameter that determines the magnification at which the systemwill capture image data. Alternatively, in an MRI system, theconfiguration module 200 may set a parameter that determines thefrequency of image slices captured. A variety of image captureparameters can be established by the configuration module 200 as will beunderstood by those skilled in the art. Advantageously, the oneembodiment, the configuration module 200 is configures to cooperate withthe collaboration server 40 to establish these parameters. This allowsthe collaboration server 40 to ensure that appropriate medical imagedata is made part of the medical image based case. For example, forcertain tissue types or for certain disease types, image data may needto be captured as a certain magnification. The configuration module 200operates to cooperate with the collaboration server 40 to set aparameter on the SMICD 50 that will cause the digital medical image datato be captured at the desired magnification.

The image capture module 210 is configured to capture and store digitalmedical image data as appropriate for the particular type of SMICD 50,e.g., digital pathology system, MRI system, CT system, X-ray system,etc.

The upload module 220 is configured to cooperate with the collaborationserver 40 to securely upload digital medical image data to thecollaboration server 40. For example, the upload module 220 may encryptthe medical image data prior to sending the medical image data to thecollaboration server 40. Additionally, the upload module 220 may use asecure data communication protocol to send the encrypted medical imagedata to the collaboration server 40.

In addition to sending the digital medical image data to thecollaboration server 40, the upload module 220 may also send metadataand other information to the collaboration server 40. For example, theupload module 220 may also provide the collaboration server 40 withinformation from multiple sources such as an LIS, other imaging systems(e.g., a digital camera that captures a gross image), reports such asradiology reports, pharmacy reports, patient information, patientprescription information, patient insurance information, requestingsystem billing information, ancillary test results (e.g,immunohistochemistry, flow cytometry, special stains information,genetics information, etc.), LIS information, requesting system 10 caseidentification information, requesting system 10 preferred consultingsystem information, and any other information maintained by therequesting system 10.

In an alternative embodiment, such additional information is provided tothe collaboration server 40 by another device that is part of therequesting system 10 and not by the SMICD 50, which may for example be aspecialized medical imaging device that is unable to host and executethe upload module 220.

FIG. 3 is a block diagram illustrating an example collaboration server40 in a system for medical image based collaboration according to anembodiment of the invention. In the illustrated embodiment, the server40 comprises SMICD command module 300, a case module 310, a directorymodule 320, an image viewing module 330, an image analysis module 340, auser interface module 350, a data mining module 360, a repository module370 and an admin/billing module 380. The collaboration server 40 alsohas a data storage area 45, which may include both persistent andvolatile storage as described above.

SMICD command module 300 is configured to interface via network 90 withthe configuration module 200 and the upload module 220 of the SMICD 50.The SMICD command module 300 is configured to provide information andinstructions to the SMICD 50 and to receive requests and informationfrom the SMICD 50. In one embodiment, the SMICD command module 300coordinates the workflow for medical image based collaboration incooperation the various other modules on the collaboration server 40.For example, the command module 300 may cooperate with the case module310 to create and complete a medical image based case, may cooperatewith the directory module 320 to allow a requesting system to search thedirectory of available consulting systems (individuals and groups), maycooperate with the image viewing module 330 to provide medical imagebased case information to a consulting system, cooperate with the imageanalysis module 340 and the case module 310 to update a medical imagebased case with image analysis information, cooperate with the userinterface module 350 to provide information on the display of a userdevice or a viewing device, cooperate with the data mining module 360 toanalyze medical image based information to identify trends in data andprovide other analytical information based on such analyses, cooperatewith the repository module 370 to archive medical image based caseinformation for later use, and cooperate with the admin/billing module380 to effect payment for medical image based collaboration and providereports to both consulting systems and requesting systems.

In one embodiment, the SMICD command module 300 receives an electronicrequest from a requesting system 10 to create a medical image basedcase. The request may be received from an operator of a computer deviceat the requesting system 10 or it may be received directly from a SMICD50. In response, the command module 300 creates a medical image basedcase and establishes a minimum data set required to complete the case.In one embodiment, the minimum data set is a digital medical image and acase number. The command module 300 is configured to assign a casenumber to the medical image based case. In one embodiment the casenumber may include a portion that is associated with an LIS systememployed by the requesting system. The command module 300 can requestadditional information that is to be made part of the medical imagebased case, for example by querying the requesting system or by directlyquerying the LIS system employed by the requesting system. Once themedical image based case is complete, the command module 300 notifiesthe consulting system and then cooperates with the image viewing module330 to allow the consulting system to view the medical image based caseinformation, for example via a browser running on a computer systemassociated with the consulting system.

The command module 300 is also configured to receive medical image basedcase analysis information from the consulting system and store thatinformation in association with the medical image based case and then tocooperate with the user interface module 350 to provide the medicalimage based information, including the medical image based case analysisinformation to the requesting system.

The command module 300 is also configured to receive uploaded medicalimage data, either in cooperation with an upload module 220 orotherwise. For example, in an embodiment where the requesting systemdoes not use a smart medical image capture device, an operator at therequesting system may login to the collaboration server 40 and interactwith the SMICD command module 300 via the user interface module 350 andprovide digital medical image data. This may be accomplished by thecommand module 300 presenting the operator with a file upload window toallow the operator to select a digital medical image file located in adata storage area at the requesting system. Additional and alternativeinformation may also be provided from the requesting system in thisfashion and accordingly various reports, gross images, LIS information,ancillary test results and the like can be incorporated into the medicalimage based case in this fashion.

Case module 310 is configured to create and store medical image basedcases and cooperate with the command module 300 to establish a set ofminimum required data to complete a medical image based case. Forexample, in Table 1 below, the case module 300 maintains a set ofminimum required information for a plurality of medical conditions andtracks the status of any new medical image based case until the variousrequired elements are included in the case information to allow themedical image based case to be determined to be complete.

MEDICAL CONDITION MINIMUM REQUIRED INFORMATION CONDITION_1 X X XCONDITION_2 X X X CONDITION_3 X X X

Case module 310 may also cooperate with image analysis module 340 toupdate the medical image based case information to include imageanalysis information provided by the image analysis module 340. The casemodule 310 may also maintain a current status of the medical image basedcase in order to facilitate tracking and management of the workflowassociated with the medical image based case. In one embodiment, thecurrent status of the case may include whether the case is pending orcomplete, whether the consulting system has requested additionalinformation (and if so, who is responsible to provide the additionalinformation). Advantageously, the case module 310 may cooperate with thedirectory module 320 to maintain a set of preferences for consultingsystems that are individuals or groups and then apply those preferencesto individual medical image based cases that are associated with theparticular consulting systems that are those individuals or groups.

Directory module 320 is configured to maintain in a data storage area alist of consulting systems and their respective availabilities that canbe searched by requesting systems in need of a consulting system. Asdiscussed above, the directory module 320 may also maintain preferencesof each consulting system so that medical image based cases assigned toa particular consulting system are properly seeded with the informationdesired by the particular consulting system. This capabilityadvantageously reduces the turn-around-time (“TAT”) associated withproviding a consultation analyses.

In one embodiment, the directory module 320 may include additionalinformation for each consulting system. For example, in Table 2 belowthe directory module 320 maintains subspecialty information for eachconsulting system in addition to a price per case that is charged by therespective consulting system for the particular subspecialty, aturn-around-time and an availability that is expressed as the volume ofcases per month that the consulting system can process.

PRICE CONSULTING SUB- PER SYSTEM SPECIALTY CASE TAT VOLUME CONSULTING_1BREAST $210 4D  40/MO CONSULTING_2 LUNG $225 2D  25/MO CONSULTING_3PROSTATE $275 3D 200/MO

Image viewing module 330 is configured to provide a consulting system ora requesting system with medical image based case information includingmetadata and digital medical image data. The image viewing module 330 isadvantageously capable of presenting such data in a browser window of aconsulting system's computer. The image viewing module 330 is alsocapable of providing this same information to another party such as therequesting party or some other third party with the appropriate accesscredentials.

Image analysis module 340 is configured to store and execute imageanalysis algorithms on the medical image based case information in orderto provide more robust information and data to the requesting system andthe consulting system alike. The image analysis module 340 is alsoconfigured to cooperate with the case module 310 to store such imageanalysis information in association with each medical image based caseso analyzed.

The image analysis module 340 may also be employed to analyze digitalmedical image data that is part of a medical image based case anddetermine if the digital medical image data is appropriate for themedical image based case. For example, if the particular condition ortissue type that is the subject of the medical image based case requiresa digital medical image at a particular resolution, the image analysismodule 340 is configured to analyze the digital medical image data anddetermine if the digital medical image data meets the requiredparameters for the medical image based case. As discussed above, suchparameters may be established in advance of capturing the digitalmedical image by the SMICD command module 300 in cooperation with theconfiguration module 200 at the requesting system.

User interface module 350 is configured to present information on adisplay at the requesting system or the consulting system and receiveinput and instructions from an operator and provide such input andinstructions to, for example, the SMICD command module 300.

Data mining module 360 is configured to analyze medical image based caseinformation stored in the data storage area and identify trends andevents to facilitate improved medical image based collaboration byrequesting systems and consulting systems. For example, the data miningmodule 360 can identify major and minor discrepancies based on ananalysis of all of the medical image based collaborations for arequesting system. Specifically, the data mining module 360 may comparethe analysis information provided to the requesting system by aconsulting system for a particular medical condition against the initialdiagnosis information that is stored as part of the medical image basedcase. The data mining module 360 may make this comparison across allmedical image based cases for a particular requesting system andcalculate a major and minor discrepancy rate.

Advantageously, if the major discrepancy rate for the requesting systemis sufficiently low, then the requesting system may be able to reducefuture costs by eliminating consultations for the particular medicalcondition. Similarly, if the major discrepancy rate for the requestingsystem is sufficiently high then the requesting system may be able toimprove accuracy of future diagnoses by requiring consultations in allinstances of the particular medical condition.

The data mining module 360 is also configured to identify areas wheretraining could be beneficial for a requesting system or a consultingsystem and to conduct companion diagnostics image analysis. The datamining module 360 is also configured to analyze information related torejected image data and provide quality assessments of at least medicalimaging services or specimen preparation laboratories.

Repository module 370 is configured to send identified medical imagebased cases to a repository server for archival and storage and analysisfor decision support and educational purposes. The repository module 370may also interface with an operator via the user interface module 350 tofacilitate searching of the repository and facilitate the use of thedecision support capabilities of the repository 70 by the operator.Advantageously, the repository module 370 may assist an operator inusing certain sophisticated visual search capabilities offered by therepository 70.

Admin/billing module 380 is configured to bill requesting systems forservices provided by the collaboration server and/or the consultingsystem. The admin/billing module 380 is also configured to payconsulting systems for services provided by the consulting systems tothe collaboration server 40 and/or the requesting system. Theadmin/billing module 380 is also configured to provide a robust reportgenerating capability for requesting systems and consulting systems. Inone embodiment, the admin/billing module 380 works in cooperation withthe data mining module 360 to provide reports and other informationincluding data mining module 360 analysis regarding a requestingsystem's major and minor discrepancies and/or a consulting system'sareas of strength. The admin/billing module 380 can therefore assist arequesting system with identifying areas where its medical professionalsmay need some future training and assist a consulting system withidentifying areas where its medical professionals can market expandedconsulting services or training services.

FIG. 4 is a flow diagram illustrating an example process for initiatingmedical image based collaboration by a requesting system according to anembodiment of the invention. The illustrated process may be carried outby a system such as previously described with respect to FIGS. 1-3 .Initially, in step 400 an operator at a requesting system logs into thecollaboration server and requests that a case be created in step 405. Inresponse to this request, the collaboration server creates a datastructure that resides in a memory of the collaboration server andstores the medical image based case information. The collaborationserver assigns a case number to the newly created case and the operatorat the requesting system receives the case number in step 410. Next, theoperator at the requesting system obtains the digital medical image instep 415, for example, by instructing a digital medical imaging deviceto capture a digital medical image. Alternatively, if the digitalmedical image already exists, the operator may simply browse ahierarchical file system (or other type) and select the desired digitalmedical image. Once the digital medical image has been obtained (by realtime image capture or by selecting from a file system), in step 420 therequesting system uploads the digital medical image in association withthe case number previously received in step 410.

In this fashion, an operator at a requesting system can effectivelycreate and complete a number of medical image based cases on thecollaboration server. In an embodiment where additional information isrequired to meet the minimum required data to complete a medical imagebased case, the operator can either upload the additional requiredinformation in step 420 or allow the collaboration server to interfacewith an LIS system or other data source at the requesting system orelsewhere to obtain any additional information needed to complete themedical image based case.

FIG. 5 is a flow diagram illustrating an example process forautomatically initiating medical image based collaboration by a smartmedical image capture device according to an embodiment of theinvention. The illustrated process may be carried out by a system suchas previously described with respect to FIGS. 1-3 . Initially, in step430 the SMICD receives a first slide. In this example embodiment, theSMICD is a digital pathology system that is configured with anautoloader having a one hundred and twenty (120) physical glassmicroscope slide capacity. Accordingly, the SMICD receives a first slideby way of the autoloader and then in step 435 the SMICD scans or readsone or more barcodes that are affixed to the glass microscope slide. Aswill be understood by those skilled in the art, the one or morebarcodes, when decoded, provide access to certain information about thespecimen on the glass microscope slide and the patient to which thespecimen belongs. For example, the information about the specimen mayinclude what stains the specimen was treated with and the informationabout the patient may include demographic information, medical recordinformation, LIS information and the like.

Next, in step 440 the SMICD sends an image of the barcode(s), thedecoded barcode, or the information corresponding to the barcode to thecollaboration server. In turn, the collaboration server creates amedical image based case in step 440 and sends a case number back to theSMICD, as shown in step 445. Next, the SMICD obtains the digital medicalimage in step 450. In this particular example embodiment, the digitalpathology system digitally scans the glass microscope slide to create awhole slide image. Alternatively, the digital pathology system may onlydigitally scan a portion of the specimen on the slide. Advantageously,any type of digital pathology system that creates a digital image of aspecimen on a glass microscope slide may be employed.

Once the digital medical image has been obtained, the image is uploadedto the collaboration server in association with the case number as shownin step 455. In one embodiment, this completes the medical image basedcase on the collaboration server. If additional information is requiredto meet the minimum required data for the medical image based case, suchdata can be provide to or obtained by the collaboration server aspreviously described.

Continuing with the present example of the digital pathology systemSMICD, if the autoloader has additional unscanned slides, as determinedin step 460, the SMICD loops back to step 430 and receives another glassmicroscope slide and the process of creating another medical image basedcase proceeds. Alternatively, if all 120 glass microscope slides fromthe autoloader have been scanned and medical image based cases createdfor each glass microscope slide, then the process ends in step 465.

FIG. 6 is a flow diagram illustrating an example process for creating acomplete medical image based case according to an embodiment of theinvention. The illustrated process may be carried out by a system suchas previously described with respect to FIGS. 1-3 . Initially, in step470 the collaboration server receives a request to create a new medicalimage based case and then in step 475 the collaboration server createsthe medical image based case. Next in step 480 the collaboration serverdetermines the minimum data required to complete the case.

The minimum data required to complete a case may be predicated upon thesubject matter of the case. For example, if the medical image based caseis of a certain tissue type or a certain pathological condition or thelike, then the minimum data required may be established by apredetermined list of requirements that are associated with theparticular tissue type, certain pathological condition or the like. Thecollaboration server may obtain information about the tissue type orpathological condition from LIS information or other metadatainformation that was provided to the collaboration server in associationwith the case number. Additionally, the collaboration server may requestinformation including tissue type, pathological condition or the likefrom one or more data sources at the requesting system or from one ormore data sources elsewhere that are not affiliated with the requestingsystem. For example, industry groups or medical professional groups mayestablish minimum standards that can be used by the collaboration serveras minimum data requirements. In one embodiment, the collaborationserver maintains a table of minimum data requirements for a plurality oftypes of medical image based cases.

Once the minimum data required has been determined and associated withthe medical image based case, the collaboration server proceeds toreceive data and store the received data as part of, or in associationwith, the medical image based case as shown in step 485. Thecollaboration server continues to evaluate whether all of the minimumdata required has been received and stored for the medical image basedcase as indicated by step 490 and the continuing loop between evaluatingif the case is complete in step 490 and receiving data in step 485. Oncethe collaboration server has determined that the medical image basedcase is complete in step 490, the collaboration server sends a notice toone or more consulting systems that are associated with the medicalimage based case. Advantageously, the notice indicates that the medicalimage based case is available for analysis by the one or more consultingsystems.

FIG. 7 is a flow diagram illustrating an example process for configuringa smart medical image capture device in accordance with medical imagebased case parameters according to an embodiment of the invention. Theillustrated process may be carried out by a system such as previouslydescribed with respect to FIGS. 1-3 . Initially, in step 500 thecollaboration server receives a request to create a case from an SMICDat a requesting system. Alternatively, the collaboration server mayreceive the request from an operator at the requesting system where theoperator is using a communication device that is not an SMICD. Next, instep 505 the collaboration server obtains certain information for themedical image based case, for example, the collaboration server mayreceive barcode or LIS or other information directly from the SMICDdevice or from other data sources. Alternatively, the operator mayupload or otherwise provide such information to the collaborationserver. Next, in step 510 the collaboration server creates the case andas part of creating the case the collaboration server assigns a casenumber to the medical image based case. In one embodiment, the casenumber may be a combination of a requesting system case number and aconsulting system case number. Alternatively, the case number may be acombination of a requesting system case number and a collaborationserver case number or the case number may be a combination of arequesting entity case number and a consulting system case number and acollaboration server case number. A variety of options for case numbersmay be employed, with workflow advantages realized from repurposing therequesting system case number and the consulting system case number.

After the case has been created, the collaboration server configures theSMICD. This configuration of the SMICD can be accomplished by thecollaboration server by sending a single command or a series of commandsto the SMICD to cause the SMICD to execute the commands and therebyestablish the desired parameters for the medical image capture process.In one embodiment, configuring the SMICD establishes the parametersunder which the medical imaging process takes place. For example,illumination characteristics, magnification, resolution, speed,frequency, area and other general and/or specific medical imagingcharacteristics for the particular type of SMICD can be establishedthrough the configuration process. Once the SMICD has been configured,the collaboration server receives image data and metadata in step 520and analyzes the image data and metadata to confirm that the image datacorroborates that the digital medical image was captured using theparameters that were established when the SMICD was configured withrespect to step 515. If the analysis of the image data confirms that thecorrect parameters were used, the collaboration server updates the casefile with the image data and the metadata received in step 520.Alternatively, if the analysis of the image data confirms or suggeststhat the correct parameters were not used, the collaboration server candiscard the image data and the metadata received in step 520.

In one embodiment, analysis of the image data includes determining theresolution of the digital medical image, determining the magnificationof the digital medical image, determining the image quality of thedigital medical image, determining the illumination characteristics ofthe digital medical image, determining if the digital medical image wascaptured under fluorescent imaging conditions, determining the tissuetype of the specimen, determining the color space of the digital medicalimage and the like.

FIG. 8 is a flow diagram illustrating an example process for searching adirectory of consulting systems according to an embodiment of theinvention. The illustrated process may be carried out by a system suchas previously described with respect to FIGS. 1-3 . Initially, in step600 the collaboration server obtains medical image based caseinformation, e.g., from a data storage area, and analyzes the medicalimage based case information in step 605. Based on the analysis, in step610 the collaboration server searches a directory of consulting systems.As previously discussed, a consulting system may be an individualconsultant or a group of consultants. Based on the search results, thecollaboration server compiles an initial list of possible consultingsystems in step 615. In one embodiment, the initial list may be compiledbased on a match of the medical image based case type and a consultingsystem's subspecialty.

Once an initial list has been compiled by the collaboration server, instep 620 the sever obtains additional parameters from the requestingsystem and filters the compiled list of consulting systems based on theadditional parameters, as shown in step 625. Next, in step 630 thecollaboration system provides the filtered list of consulting systems tothe requesting system. Optionally, the collaboration server may loopback and obtain additional or alternative parameters from the requestingsystem and then apply the additional or alternative parameters tofurther filter the initial list of possible consulting systems. Thisprocess of reviewing and filtering may continue through multipleiterations until such time as the requesting system is satisfied withthe list of available consulting systems.

In one embodiment, the initial compiled list or the filtered list (orboth) may be compiled or filtered based on the availability of theconsulting system. Accordingly, if a particular consulting system iscurrently too busy or is currently on vacation, then that particularconsulting system may advantageously be excluded from both the initialcompiled list and the filtered list.

FIG. 9 is a block diagram illustrating an example workflow in a systemfor medical image based collaboration according to an embodiment of theinvention. The illustrated process may be carried out by a system suchas previously described with respect to FIGS. 1-3 . In the illustratedembodiment, the system comprises a requesting system 10 communicativelycoupled with a consulting system 30 via a collaboration server 40 and anetwork 90. Initially, in step 650 a medical image is digitized at therequesting system 10 and then uploaded in step 660 to a data storagearea at the collaboration server 40. As shown, LIS case informationand/or additional information 655 may be provided to the collaborationserver 40 at the time of the image upload 660 or during case review 665or consult request 670.

Once the digital medical image has been uploaded to the server and themedical image based case has been created, the next steps in theworkflow are performed at the server 40 in cooperation with therequesting system 10 and/or the consulting system 40. For example, instep 665 the collaboration server 40 facilitates a review of the medicalimage based case by the requesting system 10 to allow the requestingsystem 10 to ensure that the medical image based case is complete. Atthis step, additional information such as LIS information 655 may beuploaded to the collaboration server 40 and included with the medicalimage based case. In one embodiment, this review can be conducted by anoperator at the requesting system 10.

Similarly, the collaboration server 40 next receives a consult requestin step 670 from the requesting system 10 and solely or interactivelywith the requesting system 10 searches a directory of consulting systemsto identify one or more consulting systems appropriate for theparticular medical image based case. Note that at this step during theworkflow, additional information such as LIS information 655 may beadded to the medical image base case.

In step 675 the collaboration server 40 assigns a consulting system 30to the medical image based case and in one embodiment the medical imagebased case information is exported to an LIS system managed andmaintained by the consulting system 30. Next in step 680, the consultingsystem 30 analyzes the medical image based case information receivedfrom the collaboration server 40 and prepares a consultant analysis andsends the consultant analysis to the collaboration server 40 for storagewith the medical image based case. In one embodiment, a companion LISreport or other reports from the consulting system 30 may be includedwith the consultant analysis and ultimately made part of the medicalimage based case. The collaboration server 40 then provides theconsultant analysis to the requesting system 10 to complete thecollaboration workflow. Advantageously, additional digital medicalimages may be digitized and uploaded simultaneously or serially toprovide larger scale collaboration between one or more requestingsystems 10 and one or more consulting systems 30.

Additionally, in one embodiment, during the consulting system 30 review,the consulting system 30 may request that additional information beincluded with the medical image based case. In response, thecollaboration server 40 may update the status of the medical image basedcase and send a notice to the requesting system 10 regarding the requestfor additional information. Once the requesting system 10 has providedthe additional information, the collaboration server 40 may again updatethe status of the medical image based case and notify the consultingsystem 30 that the updated medical image based case is ready for reviewby the consulting system 30. Multiple iterations of requests foradditional information may be employed in order to ensure that themedical image based case is complete.

FIG. 10 is a block diagram illustrating an example wired or wirelesssystem 550 that may be used in connection with various embodimentsdescribed herein. For example the system 550 may be used as or inconjunction with a requesting system, consulting system, medical imagecapture device, smart medical image capture device, server or repositoryas previously described with respect to FIGS. 1-3 . The system 550 canbe a personal computer, computer server, personal digital assistant,smart phone, tablet computer or the like, a medical image capture systemsuch as a digital slide scanning system, radiology imaging system,magnetic resonance imaging system, computed axial tomography system,X-ray system or the like or any other processor enabled device that iscapable of wired or wireless data communication. Other computer systemsand/or architectures may be also used, as will be clear to those skilledin the art. Specialty components needed for specific purposes such asmedical imaging can be integrated into the system 550 as will beunderstood by those skilled in the art and will therefore not bedescribed here in detail. One example of a digital slide scanning systemis described in U.S. Pat. No. 6,711,283, which is incorporated herein byreference in its entirety.

The system 550 preferably includes one or more processors, such asprocessor 560. Additional processors may be provided, such as anauxiliary processor to manage input/output, an auxiliary processor toperform floating point mathematical operations, a special-purposemicroprocessor having an architecture suitable for fast execution ofsignal processing algorithms (e.g., digital signal processor), a slaveprocessor subordinate to the main processing system (e.g., back-endprocessor), an additional microprocessor or controller for dual ormultiple processor systems, or a coprocessor. Such auxiliary processorsmay be discrete processors or may be integrated with the processor 560.

The processor 560 is preferably connected to a communication bus 555.The communication bus 555 may include a data channel for facilitatinginformation transfer between storage and other peripheral components ofthe system 550. The communication bus 555 further may provide a set ofsignals used for communication with the processor 560, including a databus, address bus, and control bus (not shown). The communication bus 555may comprise any standard or non-standard bus architecture such as, forexample, bus architectures compliant with industry standard architecture(“ISA”), extended industry standard architecture (“EISA”), Micro ChannelArchitecture (“MCA”), peripheral component interconnect (“PCI”) localbus, or standards promulgated by the Institute of Electrical andElectronics Engineers (“IEEE”) including IEEE 488 general-purposeinterface bus (“GPIB”), IEEE 696/S-100, and the like.

System 550 preferably includes a main memory 565 and may also include asecondary memory 570. The main memory 565 provides storage ofinstructions and data for programs executing on the processor 560. Themain memory 565 is typically semiconductor-based memory such as dynamicrandom access memory (“DRAM”) and/or static random access memory(“SRAM”). Other semiconductor-based memory types include, for example,synchronous dynamic random access memory (“SDRAM”), Rambus dynamicrandom access memory (“RDRAM”), ferroelectric random access memory(“FRAM”), and the like, including read only memory (“ROM”).

The secondary memory 570 may optionally include a internal memory 575and/or a removable medium 580, for example a floppy disk drive, amagnetic tape drive, a compact disc (“CD”) drive, a digital versatiledisc (“DVD”) drive, etc. The removable medium 580 is read from and/orwritten to in a well-known manner. Removable storage medium 580 may be,for example, a floppy disk, magnetic tape, CD, DVD, SD card, etc.

The removable storage medium 580 is a non-transitory computer readablemedium having stored thereon computer executable code (i.e., software)and/or data. The computer software or data stored on the removablestorage medium 580 is read into the system 550 for execution by theprocessor 560.

In alternative embodiments, secondary memory 570 may include othersimilar means for allowing computer programs or other data orinstructions to be loaded into the system 550. Such means may include,for example, an external storage medium 595 and an interface 570.Examples of external storage medium 595 may include an external harddisk drive or an external optical drive, or and external magneto-opticaldrive.

Other examples of secondary memory 570 may include semiconductor-basedmemory such as programmable read-only memory (“PROM”), erasableprogrammable read-only memory (“EPROM”), electrically erasable read-onlymemory (“EEPROM”), or flash memory (block oriented memory similar toEEPROM). Also included are any other removable storage media 580 andcommunication interface 590, which allow software and data to betransferred from an external medium 595 to the system 550.

System 550 may also include an input/output (“I/O”) interface 585. TheI/O interface 585 facilitates input from and output to external devices.For example the I/O interface 585 may receive input from a keyboard ormouse and may provide output to a display. The I/O interface 585 iscapable of facilitating input from and output to various alternativetypes of human interface and machine interface devices alike.

System 550 may also include a communication interface 590. Thecommunication interface 590 allows software and data to be transferredbetween system 550 and external devices (e.g. printers), networks, orinformation sources. For example, computer software or executable codemay be transferred to system 550 from a network server via communicationinterface 590. Examples of communication interface 590 include a modem,a network interface card (“NIC”), a wireless data card, a communicationsport, a PCMCIA slot and card, an infrared interface, and an IEEE 1394fire-wire, just to name a few.

Communication interface 590 preferably implements industry promulgatedprotocol standards, such as Ethernet IEEE 802 standards, Fiber Channel,digital subscriber line (“DSL”), asynchronous digital subscriber line(“ADSL”), frame relay, asynchronous transfer mode (“ATM”), integrateddigital services network (“ISDN”), personal communications services(“PCS”), transmission control protocol/Internet protocol (“TCP/IP”),serial line Internet protocol/point to point protocol (“SLIP/PPP”), andso on, but may also implement customized or non-standard interfaceprotocols as well.

Software and data transferred via communication interface 590 aregenerally in the form of electrical communication signals 605. Thesesignals 605 are preferably provided to communication interface 590 via acommunication channel 600. In one embodiment, the communication channel600 may be a wired or wireless network, or any variety of othercommunication links. Communication channel 600 carries signals 605 andcan be implemented using a variety of wired or wireless communicationmeans including wire or cable, fiber optics, conventional phone line,cellular phone link, wireless data communication link, radio frequency(“RF”) link, or infrared link, just to name a few.

Computer executable code (i.e., computer programs or software) is storedin the main memory 565 and/or the secondary memory 570. Computerprograms can also be received via communication interface 590 and storedin the main memory 565 and/or the secondary memory 570. Such computerprograms, when executed, enable the system 550 to perform the variousfunctions of the present invention as previously described.

In this description, the term “computer readable medium” is used torefer to any non-transitory computer readable storage media used toprovide computer executable code (e.g., software and computer programs)to the system 550. Examples of these media include main memory 565,secondary memory 570 (including internal memory 575, removable medium580, and external storage medium 595), and any peripheral devicecommunicatively coupled with communication interface 590 (including anetwork information server or other network device). Thesenon-transitory computer readable mediums are means for providingexecutable code, programming instructions, and software to the system550.

In an embodiment that is implemented using software, the software may bestored on a computer readable medium and loaded into the system 550 byway of removable medium 580, I/O interface 585, or communicationinterface 590. In such an embodiment, the software is loaded into thesystem 550 in the form of electrical communication signals 605. Thesoftware, when executed by the processor 560, preferably causes theprocessor 560 to perform the inventive features and functions previouslydescribed herein.

The system 550 also includes optional wireless communication componentsthat facilitate wireless communication over a voice and over a datanetwork. The wireless communication components comprise an antennasystem 610, a radio system 615 and a baseband system 620. In the system550, radio frequency (“RF”) signals are transmitted and received overthe air by the antenna system 610 under the management of the radiosystem 615.

In one embodiment, the antenna system 610 may comprise one or moreantennae and one or more multiplexors (not shown) that perform aswitching function to provide the antenna system 610 with transmit andreceive signal paths. In the receive path, received RF signals can becoupled from a multiplexor to a low noise amplifier (not shown) thatamplifies the received RF signal and sends the amplified signal to theradio system 615.

In alternative embodiments, the radio system 615 may comprise one ormore radios that are configured to communicate over various frequencies.In one embodiment, the radio system 615 may combine a demodulator (notshown) and modulator (not shown) in one integrated circuit (“IC”). Thedemodulator and modulator can also be separate components. In theincoming path, the demodulator strips away the RF carrier signal leavinga baseband receive audio signal, which is sent from the radio system 615to the baseband system 620.

If the received signal contains audio information, then baseband system620 decodes the signal and converts it to an analog signal. Then thesignal is amplified and sent to a speaker. The baseband system 620 alsoreceives analog audio signals from a microphone. These analog audiosignals are converted to digital signals and encoded by the basebandsystem 620. The baseband system 620 also codes the digital signals fortransmission and generates a baseband transmit audio signal that isrouted to the modulator portion of the radio system 615. The modulatormixes the baseband transmit audio signal with an RF carrier signalgenerating an RF transmit signal that is routed to the antenna systemand may pass through a power amplifier (not shown). The power amplifieramplifies the RF transmit signal and routes it to the antenna system 610where the signal is switched to the antenna port for transmission.

The baseband system 620 is also communicatively coupled with theprocessor 560. The central processing unit 560 has access to datastorage areas 565 and 570. The central processing unit 560 is preferablyconfigured to execute instructions (i.e., computer programs or software)that can be stored in the memory 565 or the secondary memory 570.Computer programs can also be received from the baseband processor 610and stored in the data storage area 565 or in secondary memory 570, orexecuted upon receipt. Such computer programs, when executed, enable thesystem 550 to perform the various functions of the present invention aspreviously described. For example, data storage areas 565 may includevarious software modules (not shown) that are executable by processor560.

Various embodiments may also be implemented primarily in hardware using,for example, components such as application specific integrated circuits(“ASICs”), or field programmable gate arrays (“FPGAs”). Implementationof a hardware state machine capable of performing the functionsdescribed herein will also be apparent to those skilled in the relevantart. Various embodiments may also be implemented using a combination ofboth hardware and software.

Furthermore, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and method stepsdescribed in connection with the above described figures and theembodiments disclosed herein can often be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled persons can implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the invention. In addition, the grouping of functions within amodule, block, circuit or step is for ease of description. Specificfunctions or steps can be moved from one module, block or circuit toanother without departing from the invention.

Moreover, the various illustrative logical blocks, modules, and methodsdescribed in connection with the embodiments disclosed herein can beimplemented or performed with a general purpose processor, a digitalsignal processor (“DSP”), an ASIC, FPGA or other programmable logicdevice, discrete gate or transistor logic, discrete hardware components,or any combination thereof designed to perform the functions describedherein. A general-purpose processor can be a microprocessor, but in thealternative, the processor can be any processor, controller,microcontroller, or state machine. A processor can also be implementedas a combination of computing devices, for example, a combination of aDSP and a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

Additionally, the steps of a method or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumincluding a network storage medium. An exemplary storage medium can becoupled to the processor such the processor can read information from,and write information to, the storage medium. In the alternative, thestorage medium can be integral to the processor. The processor and thestorage medium can also reside in an ASIC.

The above description of the disclosed embodiments is provided to enableany person skilled in the art to make or use the invention. Variousmodifications to these embodiments will be readily apparent to thoseskilled in the art, and the generic principles described herein can beapplied to other embodiments without departing from the spirit or scopeof the invention. Thus, it is to be understood that the description anddrawings presented herein represent a presently preferred embodiment ofthe invention and are therefore representative of the subject matterwhich is broadly contemplated by the present invention. It is furtherunderstood that the scope of the present invention fully encompassesother embodiments that may become obvious to those skilled in the artand that the scope of the present invention is accordingly not limited.

The invention claimed is:
 1. A method comprising using at least onehardware processor to: receive a request to create a medical case from arequesting system over at least one network; in response to the request,create the medical case, define a minimum dataset required for themedical case to be complete by performing acts comprising selecting theminimum dataset from a plurality of available minimum datasets based ona medical condition associated with the medical case, in advance ofcapturing medical image data to be included in the medical case,determine one or more image-capture parameters for the medical case, andsend one or more commands, over the at least one network, to a smartimage-capture device at the requesting system, to configure the smartimage-capture device according to the one or more image-captureparameters, and control the smart image-capture device to auto-load andscan a microscope slide, associated with the medical case, to capturethe medical image data according to the one or more image-captureparameters; receive the captured medical image data from the requestingsystem over the at least one network; store the medical image data inassociation with the medical case; and provide access to the medicalcase to one or more consulting systems.
 2. The method of claim 1,wherein the smart image-capture device is a digital pathology systemthat captures a whole slide image as the medical image data.
 3. Themethod of claim 1, further comprising using the at least one hardwareprocessor to determine when the medical case is complete based on theminimum dataset, wherein the one or more consulting systems are providedaccess to the medical case only after the medical case is determined tobe complete.
 4. The method of claim 1, further comprising using the atleast one hardware processor to, after providing access to the medicalcase to one or more consulting systems, receive analysis informationfrom at least one of the one or more consulting systems.
 5. The methodof claim 4, further comprising using the at least one hardware processorto, after receiving the analysis information, store the analysisinformation in association with the medical case.
 6. The method of claim5, further comprising using the at least one hardware processor toprovide access to the analysis information to the requesting system. 7.The method of claim 5, further comprising using the at least onehardware processor to, after receiving the analysis information:determine whether the medical case meets one or more predeterminedcriteria; and, when determining that the medical case meets the one ormore predetermined criteria, transmitting the medical case, includingthe medical image data and the analysis information, to an onlinetraining and education repository.
 8. The method of claim 1, wherein theone or more image-capture parameters comprise a magnification level. 9.The method of claim 1, further comprising using the at least onehardware processor to provide access to a directory of availableconsulting systems to the requesting system.
 10. The method of claim 1,further comprising using the at least one hardware processor to receivemetadata from the requesting system over the at least one network. 11.The method of claim 10, wherein the metadata comprises patient-specificdata for a patient from which a sample on the microscope slide wasobtained.
 12. The method of claim 11, wherein the patient-specific datacomprises a laboratory information system (LIS) number, wherein themethod further comprises using the at least one hardware processor toassign a case number to the medical case, and wherein the case numbercomprises the LIS number.
 13. The method of claim 10, wherein themetadata identifies a preferred consulting system, and wherein the oneor more consulting systems, to which access to the medical case isprovided, comprise the preferred consulting system.
 14. A non-transitorycomputer-readable medium having instructions stored thereon, wherein theinstructions, when executed by a processor, cause the processor to:receive a request to create a medical case from a requesting system overat least one network; in response to the request, create the medicalcase, define a minimum dataset required for the medical case to becomplete by performing acts comprising selecting the minimum datasetfrom a plurality of available minimum datasets based on a medicalcondition associated with the medical case, in advance of capturingmedical image data to be included in the medical case, determine one ormore image-capture parameters for the medical case, and send one or morecommands, over the at least one network, to a smart image-capture deviceat the requesting system, to configure the smart image-capture deviceaccording to the one or more image-capture parameters, and control thesmart image-capture device to auto-load and scan a microscope slide,associated with the medical case, to capture the medical image dataaccording to the one or more image-capture parameters; receive thecaptured medical image data from the requesting system over the at leastone network; store the medical image data in association with themedical case; and provide access to the medical case to one or moreconsulting systems.
 15. A system comprising: at least one hardwareprocessor; and one or more server software modules that are configuredto, when executed by the at least one hardware processor, receive arequest to create a medical case from a requesting system over at leastone network, in response to the request, create the medical case, definea minimum dataset required for the medical case to be complete byperforming acts comprising selecting the minimum dataset from aplurality of available minimum datasets based on a medical conditionassociated with the medical case, in advance of capturing medical imagedata to be included in the medical case, determine one or moreimage-capture parameters for the medical case, and send one or morecommands, over the at least one network, to a smart image-capture deviceat the requesting system, to configure the smart image-capture deviceaccording to the one or more image-capture parameters, and control thesmart image-capture device to auto-load and scan a microscope slide,associated with the medical case, to capture the medical image dataaccording to the one or more image-capture parameters, receive thecaptured medical image data from the requesting system over the at leastone network, store the medical image data in association with themedical case, and provide access to the medical case to one or moreconsulting systems.
 16. The system of claim 15, further comprising thesmart image-capture device, wherein the smart image-capture devicecomprises: at least one hardware processor; and one or more clientsoftware modules that are configured to, when executed by the at leastone hardware processor of the smart image-capture device, receive theone or more commands from the one or more server software modules overthe at least one network, configure the smart image-capture device andcapture the medical image data according to the one or more commands,and upload the medical image data to the one or more server softwaremodules over the at least one network.
 17. The system of claim 16,wherein the one or more client software modules are further configuredto: retrieve information for the medical case from one or more sources;and upload the information to the one or more server software modules,over the at least one network, as metadata.
 18. The system of claim 17,wherein the one or more sources comprise a laboratory information system(LIS).